Defining travel paths in parking areas

ABSTRACT

Computer program products, methods, systems, apparatus, and computing entities are provided for defining travel paths in parking areas. In one embodiment, travel paths in parking areas can be defined by connecting street networking connection points within the parking areas. In another embodiment, such defined travel paths can be merged with actual paths traveled by vehicles in the parking areas.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/249,518 filed Apr. 10, 2014, which is a continuation of U.S.application Ser. No. 13/795,258 filed Mar. 12, 2013, both of which arehereby incorporated herein in their entireties by reference.

BACKGROUND

Map vendors, such as Tele Atlas®, Telerik®, and NAVTEQ®, provide digitalmaps to a variety of clients for different purposes. For example, suchcompanies may provide digital maps to (a) Internet websites forproviding driving directions to consumers; (b) cellular companies toinclude in smartphones; (c) government agencies (e.g., the United StatesDepartment of Agriculture and Environmental Protection Agency) for usein their respective government functions; and (d) transportation andlogistics companies, such as United Parcel Service of America, Inc.(UPS), for determining and optimizing delivery routes. Unfortunately,the digital maps provided by vendors do not generally include the travelpaths in parking areas. For example, although digital maps can be usedto provide navigational information for traveling to shopping malls,hospitals, parks, recreation areas, theme parks, and/or the like, theydo not include, for example, the actual longitude and latitudecoordinates of the travel paths within the parking areas at suchlocations. For transportation and logistics companies, information abouttravel paths in parking areas can be a paramount concern for routing andscheduling operations. Accordingly, if travel paths in parking areas areunknown or undeterminable, it can greatly impact a company's efficiencyand routing and scheduling optimization.

BRIEF SUMMARY

In general, embodiments of the present invention provide methods,apparatus, systems, computing devices, computing entities, and/or thelike for defining travel paths in parking areas.

In accordance with one aspect, a method for defining travel paths inparking areas is provided. In one embodiment, the method comprises (a)for a parking area in which there is at least one travel path for theparking area that is not represented on a digital map, defining a firstset of one or more travel paths in the parking area by identifying oneor more paths traversed by one or more vehicles in the parking areabased at least in part on telematics data collected while the one ormore vehicles were traversing the parking area; and (b) updating thedigital map to include a representation of the first set of one or moretravel paths in the parking area.

In accordance with another aspect, a computer program product fordefining travel paths in parking areas is provided. The computer programproduct may comprise at least one computer-readable storage mediumhaving computer-readable program code portions stored therein, thecomputer-readable program code portions comprising executable portionsconfigured to (a) for a parking area in which there is at least onetravel path for the parking area that is not represented on a digitalmap, define a first set of one or more travel paths in the parking areaby identifying one or more paths traversed by one or more vehicles inthe parking area based at least in part on telematics data collectedwhile the one or more vehicles were traversing the parking area; and (b)update the digital map to include a representation of the first set ofone or more travel paths in the parking area.

In accordance with yet another aspect, an apparatus comprising at leastone processor and at least one memory including computer program code isprovided. In one embodiment, the at least one memory and the computerprogram code may be configured to, with the processor, cause theapparatus to (a) for a parking area in which there is at least onetravel path for the parking area that is not represented on a digitalmap, define a first set of one or more travel paths in the parking areaby identifying one or more paths traversed by one or more vehicles inthe parking area based at least in part on telematics data collectedwhile the one or more vehicles were traversing the parking area; and (b)update the digital map to include a representation of the first set ofone or more travel paths in the parking area.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will nowbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 is a diagram of a system that can be used to practice variousembodiments of the present invention.

FIG. 2 is a diagram of a data collection device that may be used inassociation with certain embodiments of the present invention.

FIG. 3 is a schematic of a mapping system in accordance with certainembodiments of the present invention.

FIG. 4 is a schematic of a mobile device in accordance with certainembodiments of the present invention.

FIG. 5 is a flowchart illustrating operations and processes that can beused in accordance with various embodiments of the present invention.

FIGS. 6-14 illustrate exemplary input and output in accordance withvarious embodiments of the present invention.

DETAILED DESCRIPTION

Various embodiments of the present invention now will be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all embodiments of the inventions are shown. Indeed, theseinventions may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. The term “or” is used herein in both the alternativeand conjunctive sense, unless otherwise indicated. The terms“illustrative” and “exemplary” are used to be examples with noindication of quality level. Like numbers refer to like elementsthroughout.

I. COMPUTER PROGRAM PRODUCTS, METHODS, AND COMPUTING ENTITIES

Embodiments of the present invention may be implemented in various ways,including as computer program products. A computer program product mayinclude a non-transitory computer-readable storage medium storingapplications, programs, program modules, scripts, source code, programcode, object code, byte code, compiled code, interpreted code, machinecode, executable instructions, and/or the like (also referred to hereinas executable instructions, instructions for execution, program code,and/or similar terms used herein interchangeably). Such non-transitorycomputer-readable storage media include all computer-readable media(including volatile and non-volatile media).

In one embodiment, a non-volatile computer-readable storage medium mayinclude a floppy disk, flexible disk, hard disk, magnetic tape, or anyother non-transitory magnetic medium, and/or the like. A non-volatilecomputer-readable storage medium may also include a punch card, papertape, optical mark sheet (or any other physical medium with patterns ofholes or other optically recognizable indicia), compact disc read onlymemory (CD-ROM), compact disc compact disc-rewritable (CD-RW), digitalversatile disc (DVD), Blu-ray disc (BD), any other non-transitoryoptical medium, and/or the like. Such a non-volatile computer-readablestorage medium may also include read-only memory (ROM), programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), flashmemory, multimedia memory cards (MMC), secure digital (SD) memory cards,Memory Sticks, and/or the like. Further, a non-volatilecomputer-readable storage medium may also include conductive-bridgingrandom access memory (CBRAM), phase-change random access memory (PRAM),ferroelectric random-access memory (FeRAM), resistive random-accessmemory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory (SONOS),racetrack memory, and/or the like.

In one embodiment, a volatile computer-readable storage medium mayinclude random access memory (RAM), dynamic random access memory (DRAM),static random access memory (SRAM), fast page mode dynamic random accessmemory (FPM DRAM), extended data-out dynamic random access memory (EDODRAM), synchronous dynamic random access memory (SDRAM), double datarate synchronous dynamic random access memory (DDR SDRAM), double datarate type two synchronous dynamic random access memory (DDR2 SDRAM),double data rate type three synchronous dynamic random access memory(DDR3 SDRAM), Rambus dynamic random access memory (RDRAM), Rambusin-line memory module (RIMM), dual in-line memory module (DIMM), singlein-line memory module (SIMM), video random access memory VRAM, cachememory, register memory, and/or the like. It will be appreciated thatwhere embodiments are described to use a computer-readable storagemedium, other types of computer-readable storage media may besubstituted for or used in addition to the computer-readable storagemedia described above.

As should be appreciated, various embodiments of the present inventionmay also be implemented as methods, apparatus, systems, computingdevices, computing entities, and/or the like. As such, embodiments ofthe present invention may take the form of an apparatus, system,computing device, computing entity, and/or the like executinginstructions stored on a computer-readable storage medium to performcertain steps or operations. However, embodiments of the presentinvention may also take the form of an entirely hardware embodimentperforming certain steps or operations.

Embodiments of the present invention are described below with referenceto block diagrams and flowchart illustrations. Thus, it should beunderstood that each block of the block diagrams and flowchartillustrations, respectively, may be implemented in the form of acomputer program product, an entirely hardware embodiment, a combinationof hardware and computer program products, and/or apparatus, systems,computing devices, computing entities, and/or the like carrying outinstructions on a computer-readable storage medium for execution. Suchembodiments can produce specifically-configured machines performing thesteps or operations specified in the block diagrams and flowchartillustrations. Accordingly, the block diagrams and flowchartillustrations support various combinations of embodiments for performingthe specified steps or operations.

II. EXEMPLARY ARCHITECTURE

The system may include one or more vehicles 100, one or more imagingdevices 105, one or more mapping systems 110, one or more GlobalPositioning System (GPS) satellites 115, one or more networks 135, oneor more radio frequency identification (RFID) readers/interrogators 140,one or more mobile devices 145, and/or the like. Each of thesecomponents, entities, devices, systems, and similar words used hereininterchangeably may be in direct or indirect communication with, forexample, one another over the same or different wired or wirelessnetworks. Additionally, while FIG. 1 illustrates the various systementities as separate, standalone entities, the various embodiments arenot limited to this particular architecture.

a. Exemplary Vehicle

In various embodiments, a vehicle 100 may be a tractor, a truck, a car,a motorcycle, a moped, a Segway, a trailer, a tractor and trailercombination, a van, a flatbed truck, a delivery vehicle, and/or anyother form of vehicle. In one embodiment, each vehicle 100 may beassociated with a unique vehicle identifier (such as a vehicle ID) thatuniquely identifies the vehicle 100. The vehicle 100 may be mobile inthe sense that it may be able to move from one location to another underits own power. The unique vehicle ID (e.g., trailer ID, tractor ID,vehicle ID, and/or the like) may include characters, such as numbers,letters, symbols, and/or the like. For example, an alphanumeric vehicleID (e.g., “1221A445533AS445) may be associated with each vehicle 100. Inanother embodiment, the unique vehicle ID may be the license plate,registration number, or other identifying information assigned to thevehicle 100.

FIG. 1 shows one or more computing entities, devices, and/or similarwords used herein interchangeably that are associated with the vehicle100, such as an data collection device 130 or other computing entities.FIG. 2 provides a block diagram of an exemplary data collection device130 that may be attached, affixed, disposed upon, integrated into, orpart of a vehicle 100. The data collection device 130 may collecttelematics data (including location data) and transmit/send the data tothe imaging device 105, the mobile device 145, and/or the mapping system110 via one of several communication methods.

In one embodiment, the data collection device 130 may include, beassociated with, or be in communication with one or more processors 200,one or more location-determining devices or one or more location sensors120 (e.g., Global Navigation Satellite System (GNSS) sensors), one ormore telematics sensors 125, one or more real-time clocks 215, a J-Busprotocol architecture, one or more electronic control modules (ECM) 245,one or more communication ports 230 for receiving telematics data fromvarious sensors (e.g., via a CAN-bus), one or more communication ports205 for transmitting/sending data, one or more RFID tags/sensors 250,one or more power sources 220, one or more data radios 235 forcommunication with a variety of communication networks, one or morememory modules 210, and one or more programmable logic controllers (PLC)225. It should be noted that many of these components may be located inthe vehicle 100 but external to the data collection device 130.

In one embodiment, the one or more location sensors 120 may be one ofseveral components in communication with or available to the datacollection device 130. Moreover, the one or more location sensors 120may be compatible with a Low Earth Orbit (LEO) satellite system or aDepartment of Defense (DOD) satellite system. Alternatively,triangulation may be used in connection with a device associated with aparticular vehicle and/or the vehicle's operator and with variouscommunication points (e.g., cellular towers or Wi-Fi access points)positioned at various locations throughout a geographic area to monitorthe location of the vehicle 100 and/or its operator. The one or morelocation sensors 120 may be used to receive latitude, longitude,altitude, geocode, course, position, time, and/or speed data (e.g.,telematics data). The one or more location sensors 120 may alsocommunicate with the mapping system 110, the data collection device 130,and/or similar computing entities.

As indicated, in addition to the one or more location sensors 120, thedata collection device 130 may include and/or be associated with one ormore telematics sensors 125. For example, the telematics sensors 125 mayinclude vehicle sensors, such as engine, fuel, odometer, hubometer, tirepressure, location, weight, emissions, door, and speed sensors. Thetelematics data may include, but is not limited to, speed data,emissions data, RPM data, tire pressure data, oil pressure data, seatbelt usage data, distance data, fuel data, idle data, and/or the like(e.g., telematics data). The telematics sensors 125 may includeenvironmental sensors, such as air quality sensors, temperature sensors,and/or the like. Thus, the telematics data may also include carbonmonoxide (CO), nitrogen oxides (NOx), sulfur oxides (SOx), ozone (O₃),hydrogen sulfide (H₂S) and/or ammonium (NH₄) data, and/or meteorologicaldata (e.g., telematics data).

In one embodiment, the ECM 245 may be one of several components incommunication with and/or available to the data collection device 130.The ECM 245, which may be a scalable and subservient device to the datacollection device 130, may have data processing capability to decode andstore analog and digital inputs from vehicle systems and sensors. TheECM 245 may further have data processing capability to collect andpresent telematics data to the J-Bus (which may allow transmission tothe data collection device 130), and output standard vehicle diagnosticcodes when received from a vehicle's J-Bus-compatible on-boardcontrollers 240 and/or sensors.

As indicated, a communication port 230 may be one of several componentsavailable in the data collection device 130 (or be in or as a separatecomputing entity). Embodiments of the communication port 230 may includean Infrared data Association (IrDA) communication port, an data radio,and/or a serial port. The communication port 230 may receiveinstructions for the data collection device 130. These instructions maybe specific to the vehicle 100 in which the data collection device 130is installed, specific to the geographic area in which the vehicle 100will be traveling, and/or specific to the function the vehicle 100serves within a fleet. In one embodiment, the data radio 235 may beconfigured to communicate with a wireless wide area network (WWAN),wireless local area network (WLAN), wireless personal area network(WPAN), or any combination thereof. For example, the data radio 235 maycommunicate via various wireless protocols, such as 802.11, generalpacket radio service (GPRS), Universal Mobile Telecommunications System(UMTS), Code Division Multiple Access 2000 (CDMA2000), CDMA2000 1X(1xRTT), Wideband Code Division Multiple Access (WCDMA), TimeDivision-Synchronous Code Division Multiple Access (TD-SCDMA), Long TermEvolution (LTE), Evolved Universal Terrestrial Radio Access Network(E-UTRAN), Evolution-Data Optimized (EVDO), High Speed Packet Access(HSPA), High-Speed Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi),802.16 (WiMAX), ultra wideband (UWB), infrared (IR) protocols, Bluetoothprotocols, wireless universal serial bus (USB) protocols, and/or anyother wireless protocol.

In one embodiment, each vehicle 100 may have an RFID tag/sensor attachedor affixed thereto that stores the corresponding vehicle ID. Such anRFID tag/sensor can be placed inside a vehicle 100, or affixed to anouter surface of a vehicle 100, for example. The RFID tags/sensors maybe passive RFID tags/sensors, active RFID tags/sensors, semi-active RFIDtags/sensors, battery-assisted passive RFID tags/sensors, and/or thelike. Thus, the RFID tags/sensors can include some or all of thefollowing components: one or more input interfaces for receiving data,one or more output interfaces for transmitting data, a processor, aclock, memory modules, and a power source.

In another embodiment, each vehicle 100 may have its correspondingvehicle ID visible on the exterior of the vehicle 100. For example, thelicense plate number, registration number, alphanumeric characters, orother identifying information may be on the exterior of the vehicle suchthat one or more imaging devices can capture an image of the vehicle IDand properly identify it via analysis.

b. Exemplary Mapping System

FIG. 3 provides a schematic of a mapping system 110 according to oneembodiment of the present invention. In general, the term system mayrefer to, for example, one or more computers, computing devices,computing entities, mobile phones, desktops, tablets, notebooks,laptops, distributed systems, servers, blades, gateways, switches,processing devices, processing entities, relays, routers, network accesspoints, scanners, cameras, base stations, the like, and/or anycombination of devices or entities adapted to perform the functions,operations, and/or processes described herein. Such functions,operations, and/or processes may include, for example, transmitting,receiving, operating on, processing, displaying, storing, determining,creating/generating, monitoring, evaluating, comparing, and/or similarterms used herein interchangeably. In one embodiment, these functions,operations, and/or processes can be performed on data, content,information, and/or similar terms used herein interchangeably.

As indicated, in one embodiment, the mapping system 110 may also includeone or more communications interfaces 320 for communicating with variouscomputing entities, such as by communicating data, content, information,and/or similar terms used herein interchangeably that can betransmitted, received, operated on, processed, displayed, stored, and/orthe like. For instance, the mapping system 110 may communicate withvehicles 100, imaging devices 105, RFID interrogators/readers 140,mobile devices 145, and/or the like.

As shown in FIG. 3, in one embodiment, the mapping system 110 mayinclude or be in communication with one or more processing elements 305(also referred to as processors, processing circuitry, and/or similarterms used herein interchangeably) that communicate with other elementswithin the mapping system 110 via a bus, for example. As will beunderstood, the processing element 305 may be embodied in a number ofdifferent ways. For example, the processing element 305 may be embodiedas one or more complex programmable logic devices (CPLDs),microprocessors, multi-core processors, coprocessing entities,application-specific instruction-set processors (ASIPs), and/orcontrollers. Further, the processing element 305 may be embodied as oneor more other processing devices or circuitry. The term circuitry mayrefer to an entirely hardware embodiment or a combination of hardwareand computer program products. Thus, the processing element 305 may beembodied as integrated circuits, application specific integratedcircuits (ASICs), field programmable gate arrays (FPGAs), programmablelogic arrays (PLAs), hardware accelerators, other circuitry, and/or thelike. As will therefore be understood, the processing element 305 may beconfigured for a particular use or configured to execute instructionsstored in volatile or non-volatile media or otherwise accessible to theprocessing element 305. As such, whether configured by hardware orcomputer program products, or by a combination thereof, the processingelement 305 may be capable of performing steps or operations accordingto embodiments of the present invention when configured accordingly.

In one embodiment, the mapping system 110 may further include or be incommunication with non-volatile media (also referred to as non-volatilestorage, memory, memory storage, memory circuitry and/or similar termsused herein interchangeably). In one embodiment, the non-volatilestorage or memory may include one or more non-volatile storage or memorymedia 310 as described above, such as hard disks, ROM, PROM, EPROM,EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM,FeRAM, RRAM, SONOS, racetrack memory, and/or the like. As will berecognized, the non-volatile storage or memory media may storedatabases, database instances, database mapping systems, data,applications, programs, program modules, scripts, source code, objectcode, byte code, compiled code, interpreted code, machine code,executable instructions, and/or the like. The term database, databaseinstance, database mapping system, and/or similar terms used hereininterchangeably may refer to a structured collection of records or datathat is stored in a computer-readable storage medium, such as via arelational database, hierarchical database, and/or network database.

In one embodiment, the mapping system 110 may further include or be incommunication with volatile media (also referred to as volatile storage,memory, memory storage, memory circuitry and/or similar terms usedherein interchangeably). In one embodiment, the volatile storage ormemory may also include one or more volatile storage or memory media 315as described above, such as RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM,DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM, VRAM, cachememory, register memory, and/or the like. As will be recognized, thevolatile storage or memory media may be used to store at least portionsof the databases, database instances, database mapping systems, data,applications, programs, program modules, scripts, source code, objectcode, byte code, compiled code, interpreted code, machine code,executable instructions, and/or the like being executed by, for example,the processing element 305. Thus, the databases, database instances,database mapping systems, data, applications, programs, program modules,scripts, source code, object code, byte code, compiled code, interpretedcode, machine code, executable instructions, and/or the like may be usedto control certain aspects of the operation of the mapping system 110with the assistance of the processing element 305 and operating system.

As indicated, in one embodiment, the mapping system 110 may also includeone or more communications interfaces 320 for communicating with variouscomputing entities, such as by communicating data, content, information,and/or similar terms used herein interchangeably that can betransmitted, received, operated on, processed, displayed, stored, and/orthe like. For instance, the mapping system 110 may communicate withcomputing entities or communication interfaces of the vehicle 100, theimaging devices 105, RFID interrogators/readers 140, mobile devices 145,and/or the like.

Such communication may be executed using a wired data transmissionprotocol, such as fiber distributed data interface (FDDI), digitalsubscriber line (DSL), Ethernet, asynchronous transfer mode (ATM), framerelay, data over cable service interface specification (DOCSIS), or anyother wired transmission protocol. Similarly, the mapping system 110 maybe configured to communicate via wireless external communicationnetworks using any of a variety of protocols, such as GPRS, UMTS,CDMA2000, 1xRTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA,Wi-Fi, WiMAX, UWB, IR protocols, Bluetooth protocols, USB protocols,and/or any other wireless protocol. Although not shown, the mappingsystem 110 may include or be in communication with one or more inputelements, such as a keyboard input, a mouse input, a touchscreen/display input, audio input, pointing device input, joystickinput, keypad input, and/or the like. The mapping system 110 may alsoinclude or be in communication with one or more output elements (notshown), such as audio output, video output, screen/display output,motion output, movement output, and/or the like.

As will be appreciated, one or more of the mapping system's 110components may be located remotely from other mapping system 110components, such as in a distributed system. Furthermore, one or more ofthe components may be combined and additional components performingfunctions described herein may be included in the mapping system 110.Thus, the mapping system 110 can be adapted to accommodate a variety ofneeds and circumstances.

c. Exemplary Mobile Device

FIG. 4 provides an illustrative schematic representative of a mobiledevice 145 that can be used in conjunction with embodiments of thepresent invention. Mobile devices 145 can be operated by variousparties, including operators of vehicles 100. As shown in FIG. 4, amobile device 145 can include an antenna 412, a transmitter 404 (e.g.,radio), a receiver 406 (e.g., radio), and a processing element 408 thatprovides signals to and receives signals from the transmitter 404 andreceiver 406, respectively.

The signals provided to and received from the transmitter 404 and thereceiver 406, respectively, may include signaling data in accordancewith an air interface standard of applicable wireless systems tocommunicate with various entities, such as vehicles 100, imaging devices105, mapping system 110, RFID interrogators/readers 140, and/or thelike. In this regard, the mobile device 145 may be capable of operatingwith one or more air interface standards, communication protocols,modulation types, and access types. More particularly, the mobile device145 may operate in accordance with any of a number of wirelesscommunication standards and protocols. In a particular embodiment, themobile device 145 may operate in accordance with multiple wirelesscommunication standards and protocols, such as GPRS, UMTS, CDMA2000,1xRTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX,UWB, IR protocols, Bluetooth protocols, USB protocols, and/or any otherwireless protocol.

Via these communication standards and protocols, the mobile device 145can communicate with various other entities using concepts such asUnstructured Supplementary Service data (USSD), Short Message Service(SMS), Multimedia Messaging Service (MMS), Dual-Tone Multi-FrequencySignaling (DTMF), and/or Subscriber Identity Module Dialer (SIM dialer).The mobile device 145 can also download changes, add-ons, and updates,for instance, to its firmware, software (e.g., including executableinstructions, applications, program modules), and operating system.

According to one embodiment, the mobile device 145 may include alocation determining device and/or functionality. For example, themobile device 145 may include a GPS module adapted to acquire, forexample, latitude, longitude, altitude, geocode, course, and/or speeddata. In one embodiment, the GPS module acquires data, sometimes knownas ephemeris data, by identifying the number of satellites in view andthe relative positions of those satellites.

The mobile device 145 may also comprise a user interface (that caninclude a display 416 coupled to a processing element 408) and/or a userinput interface (coupled to a processing element 408). The user inputinterface can comprise any of a number of devices allowing the mobiledevice 145 to receive data, such as a keypad 418 (hard or soft), a touchdisplay, voice or motion interfaces, or other input device. Inembodiments including a keypad 418, the keypad 418 can include (or causedisplay of) the conventional numeric (0-9) and related keys (#, *), andother keys used for operating the mobile device 145 and may include afull set of alphabetic keys or set of keys that may be activated toprovide a full set of alphanumeric keys. In addition to providing input,the user input interface can be used, for example, to activate ordeactivate certain functions, such as screen savers and/or sleep modes.

The mobile device 145 can also include volatile storage or memory 422and/or non-volatile storage or memory 424, which can be embedded and/ormay be removable. For example, the non-volatile memory may be ROM, PROM,EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks,CBRAM, PRAM, FeRAM, RRAM, SONOS, racetrack memory, and/or the like. Thevolatile memory may be RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDRSDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM, VRAM, cachememory, register memory, and/or the like. The volatile and non-volatilestorage or memory can store databases, database instances, databasemapping systems, data, applications, programs, program modules, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like to implement thefunctions of the mobile device 145.

d. Exemplary Imaging Devices

Embodiments of the present invention may also include one or moreimaging devices 105 positioned at staging areas, transportation andlogistics areas, hub or center areas, on vehicles 100, carried bydelivery personnel, and/or the like. An imaging device 105 may includeone or more cameras, one or more laser scanners, one or more infraredscanners, one or more imagers, one or more video cameras, one or morestill cameras, one or more Internet Protocol (IP) cameras, one or moretraffic cameras, and/or the like. Such imaging devices 105 may beinclude one or more wide angle lenses or one or more narrow anglelenses. The imaging devices 105 may also include one or more processorsand one or more temporary memory storage areas, such as circularbuffers. Thus, the imaging devices 105 can capture images (e.g., imagedata) and store them temporarily in the temporary memory storage area orpermanently (in a separate memory storage area) within the imagingdevices 105. In one embodiment, the imaging devices 105 may also beconnected to (or include) one or more network interfaces (e.g., wired orwireless) for communicating with various computing entities. Thiscommunication may be via the same or different wired or wirelessnetworks using a variety of wired or wireless transmission protocols.This may allow the imaging devices to transmit/send images (e.g., imagedata) they capture.

In one embodiment, the imaging devices 105 can be positioned to captureimage data in zones of interest at staging areas, transportation andlogistics areas, hub or center areas, and/or the like. Exemplary zonesof interest are shown in FIGS. 6 and 7. The imaging data captured by theimaging devices 105 in the zones of interest may include (as determinedfrom analysis) a vehicle ID, image of driver's faces (for use in facialrecognition), and/or the like. The number of imaging devices 105 usedmay vary based on the desired configuration.

The resolution of the images (e.g., image data) captured by the imagingdevice 105 may be, for instance, 640 pixels by 480 pixels or higher. Inone embodiment, for night operation, the imaging devices 105 may have asensitivity of 0.5 lux or better at an optical stop equivalent of F1.Further, the imaging devices 105 may include or be used in associationwith various lighting, such as light emitting diodes (LEDs), Infraredlights, array lights, strobe lights, and/or other lighting mechanisms tosufficiently illuminate the zones of interest to capture image data foranalysis. The image data can be captured in or converted to a variety offormats, such as Joint Photographic Experts Group (JPEG), Motion JPEG(MJPEG), Moving Picture Experts Group (MPEG), Graphics InterchangeFormat (GIF), Portable Network Graphics (PNG), Tagged Image File Format(TIFF), bitmap (BMP), H.264, H.263, Flash Video (FLV), Hypertext MarkupLanguage 5 (HTML5), VP6, VP8, and/or the like.

The imaging devices 105 may also be connected to (or include) a networkinterface (e.g., the wireless Ethernet bridge) for communicating withvarious computing entities. In one embodiment, the imaging devices 105can communicate with the mapping system 110 using protocols and stacks,such as sockets. The network interface may provide the ability for eachimaging device 105 to serve as a web host with, for example, web pagesthat can be used to setup and configure the imaging devices 105.Moreover, via the web pages (or via the mapping system 110), the imagingdevices 105 can provide a live view of the zones of interest, which canbe used to aim and focus the imaging devices 105. This can also providethe functionality of controlling the exposure, gain, gamma, whitebalance, compression, and numerous other attributes of the imagingdevices 105. Thus, via the network interface, the imaging devices 105may provide access for a user to (a) remotely configure (e.g., controlthe exposure, gain, gamma, and white balance of the images) the imagingdevices 105; (b) remotely access captured images; or (c) synchronize thetime on the imaging devices 105 to a consistent network time.

e. RFID Readers/Interrogators

Embodiments of the present invention may also use one or more RFIDreaders/interrogators 140 positioned at staging areas, transportationand logistics areas, hub or center areas, and/or the like. As will berecognized, the one or more RFID readers/interrogators 140 may be usedto extract data stored or collected by the RFID tags/sensors (such asvehicle IDs) affixed to vehicles 100. For example, the one or more RFIDreaders/interrogators 140 can transmit/send a signal (e.g., a radiofrequency (RF) signal) that prompts and/or powers RFID tags/sensorsaffixed to vehicles 100 within a geographical range (e.g., a read range)to provide data from the memory of the tags/sensors to the appropriatecomputing entity or communication interface of the one or more RFIDreaders/interrogators 140.

As will be recognized, the read range may vary based on the particulartechnology being used. For example, in an embodiment using Bluetooth,the read range of a computing entity (e.g., imaging device 105 orcomputing entity or communication interface associated with a vehicle100) transmitting/sending a Bluetooth signal/request may be up to 30feet (whereas a Wi-Fi may provide a read range of 100-300 feet). Thus,RFID tags/sensors within that 30-foot read range may receive thesignal/request. Other technologies and protocols may reduce or increasethe read range. These technologies and protocols include GPRS, UMTS,CDMA2000, 1xRTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA,Wi-Fi, WiMAX, UWB, IR protocols, USB protocols, and/or any otherwireless protocol. In addition to interrogating/reading RFIDtags/sensors, these communication capabilities may enable the one ormore RFID readers/interrogators 140 to communicate with vehicles 100,imaging devices 105, mapping systems 110, mobile devices 145, and/or thelike.

In one embodiment, the one or more RFID readers/interrogators 140 cantransmit/send a signal/request (to be received by RFID tags/sensorswithin the read range) on a periodic, continuous, regular basis or inresponse to certain triggers. For example, in one embodiment, the one ormore RFID readers/interrogators 140 can transmit/send a signal/requestto be received by RFID tags/sensors within the read range every 5seconds, every 10 seconds, every 60 seconds, every 10 minutes, every 60minutes, and/or the like. In another embodiment, the one or more RFIDreaders/interrogators 140 can transmit/send a signal/request to bereceived by RFID tags/sensors within the read range in response tocertain triggers, such as a vehicle 100 entering or exiting a geofencedarea associated with a staging area, customs area, checkpoint area,and/or the like. As will be recognized, a variety of other approachesand techniques may be used to adapt to various needs and circumstances.

III. EXEMPLARY OPERATION

Reference will now be made to FIGS. 5-14. FIG. 5 is a flowchartillustrating operations and processes that can be used in accordancewith various embodiments of the present invention. FIGS. 6-14 illustrateexemplary input and output in accordance with various embodiments of thepresent invention.

a. Serviceable Addresses and Street Networks

An exemplary “serviceable address” 600 is shown in FIG. 6. A serviceableaddress 600 may be any location associated with an address or otheridentifiable location. For example, a serviceable address 600 may be aresidential location, such as one or more homes, one or more mobilehomes, one or more apartments, one or more apartment buildings, one ormore condominiums, one or more townhomes, and/or the like. Similarly, aserviceable address 600 may also be a commercial location, such as oneor more stores in a mall, one or more office buildings, one or moreoffice parks, one or more offices of an apartment complex, one or moregarages, one or more warehouses, and/or the like.

In one embodiment, a street network may be used to travel to serviceableaddresses, with one or more street network connection points 605providing the ability to enter the street network from or exit thestreet network to the serviceable address. A “street network” iscollection of navigable roads, streets, highways, paths, and/or the likerepresented in a digital map. Based on the street network, map data ofthe digital map can be used to provide directions for traveling within astreet network to serviceable addresses 600. To do so, digital maps mayinclude various information about street networks, such as the longitudeof street segments, latitude of street segments, altitude of streetsegments, speed limits of street segments, direction restrictions forstreet segments, time penalties for street segments, tax information forstreet segments, and/or other information associated with streetsegments or street networks. In one embodiment, a street segment of astreet network may be represented by a street name, an address range,and series of longitude and latitude coordinates that define the overallshape and location of the street segment.

b. Points for Serviceable Addresses

In one embodiment, each serviceable address may correspond to one ormore points at the serviceable address. One such point may be a streetnetwork connection point 605. As previously noted, a street networkconnection point 605 may be a location at which, for example, theserviceable address 600 is accessible from the street network. Forinstance, a street network connection point 605 may be an entrance to aparking area from a street network for one or more serviceable addressesor an exit from a parking area to a street network for one or moreserviceable addresses. Similarly, a street network connection point 605may be the start of a driveway, private road, recreational area, and/orthe like that corresponds to one or more serviceable addresses. FIGS. 7and 8 show four street segments surrounding a parking area. From thesefigures, it can be seen that the parking area can either be at leastentered from or exited from the four street network connection points605.

As shown in FIG. 9, each serviceable address may also be associated witha variety of other points, such as one or more freight delivery points,one or more package delivery points, and/or one or more letter deliverypoints. Such points may be the locations (e.g., driveway, door, house,or building) at which, for example, freight, packages, letters and/orthe like are actually delivered with regard to a given serviceableaddress 600 (within or outside of a street network). For instance, somebusiness may allow for letters to be delivered to the front door, whilerequiring that packages and freight be delivered at another location atthe serviceable address 600. Depending on the size of the serviceableaddress 600, the distance between such points may be considerable.Similarly, for businesses or residences that are not located directly ona street network, such as requiring access through a long driveway orparking areas, the delivery points may, for example, require a driver totravel on a driveway or parking area that extends 2/10 of a mile off ofthe street network to deliver an item or actually arrive at theserviceable address 600.

As will be recognized, not all serviceable addresses 600 have multiplestreet network connection points 605 and/or multiple delivery points.This may be the case, for instance, when a serviceable address 600represents a single dwelling home with one driveway. In otherembodiments, multiple street network connection points 605 and/ordelivery points may be necessary for a single serviceable address 600.For example, multiple street network connection points 605 may be usedif there is more than one entrance to travel to a serviceable address600 from a street network, such as a commercial location with entranceson two or three different streets (e.g., a store in a mall).

In one embodiment, each serviceable address 600 may also be associatedwith one or more access points and/or parking points parking points. Anaccess point may be a checkpoint, gate, or door, for example, that mustbe entered or passed through to access a serviceable address 600. Aparking point may be, for example, a location at which one can park at aserviceable address 600. Each serviceable address 600 may alsocorrespond to one or more door points, such as one or more front doorpoints, one or more back door points, and/or one or more side doorpoints. Such locations may identify the front, back, and/or side doorsof a particular structure at a serviceable address 600.

In one embodiment, information about the points described above andvarious other points for serviceable addresses can be collected and/orstored in a record corresponding to the serviceable address 600, such asthe record shown in FIG. 9. Such records and data may be stored as datain a digital map, for example. As will be recognized, a variety of otherapproaches and techniques can be used to adapt to various needs andcircumstances.

c. Collecting Telematics Data about Points for Serviceable Addresses

In one embodiment, information associated with the different points forserviceable addresses can be collected, identified, determined, and/orstored using a variety of techniques and approaches. For example,information regarding street network connection points 605 may be basedata provided by a digital map vendor or may include the digital mapvendor's base data combined with geo coordinates (e.g., provided by athird party). Such information about these points may be collected usingvarious methods. For example, such information may be collected via thedata collection device 130 and/or the mobile device 145 (with or withoutthe aid of the driver of the vehicle 100) and/or determined by usingmethods such interpolation.

1. Regular, Manual, or Triggered Collection of Telematics Data forServiceable Addresses

In one embodiment, the data collection device 130 or mobile device 145can provide the functionality to maintain and/or process telematics data(including location data comprising geo coordinate samples) forserviceable addresses that are visited, for example, based on items thatare delivered to or picked up from the serviceable address. In oneembodiment, the mobile device 145 can be adapted to be used to collecttelematics data (including location data comprising geo coordinatesamples) at each serviceable address visited. More specifically, themobile device 145 can be configured to collect telematics data(including location data comprising geo coordinate samples) regularly,periodically, and/or continuously or upon determining the occurrence ofone or more predefined trigger events. Such predefined trigger eventsmay include, but are not limited to: (1) scan events; (2) an electronicsignature capture event; (3) an input to the mobile device 145indicating that a driver is at a particular serviceable address 600; (4)an input or event that indicates to the mobile device 145 that an itemhas been picked up from or delivered to the serviceable address; (5) aninput specifically instructing the mobile device 145 to capture asample; (6) when the mobile device 145 determines that the vehicle 100(or driver walking with the mobile device 145) has entered or exited thestreet network; (7) when the vehicle 100 is placed in the park position;(8) ignition of the vehicle 100; and/or (8) the like. Thus, for visitsto each serviceable address 600, one or more geo coordinate samples(e.g., telematics data including location data) may be collected by themobile device 145 in response to various trigger events.

In another embodiment, the data collection device 130 can collecttelematics data (including location data comprising geo coordinatesamples) on a periodic, regular, and/or continuous basis. For example,the data collection device 130 can continuously collect telematics data(including location data comprising geo coordinate samples) as thevehicle 100 traverses street networks and/or parking areas. Moreover,the data collection device 130 can also be configured to collecttelematics data (including location data comprising geo coordinatesamples) in response to predefined trigger events, such as the vehicle100 exiting or entering a street network, the ignition of the vehicle100, and/or those discussed above with respect to the mobile device 145.

As indicated, in one embodiment, the mobile device 145 or datacollection device 130 is configured to continuously and/or periodicallystore telematics data (including location data comprising geo coordinatesamples), regardless of whether a trigger event has occurred. This maybe beneficial since geo coordinates may not always be available at anygiven time since, for example, a GPS signal could be temporarily blockedby a nearby obstruction. Thus, for instance, if a trigger event occursat a time when a geo coordinate is not immediately obtainable, the lastknown geo coordinate (or in some embodiments the next geo coordinate)can be used. In such embodiments, the mobile device 145 or datacollection device 130 may store information about the time of the geocoordinate sample and the time of the associated trigger event so thatthe mapping system 110 may use the information in determining theaccuracy of the telematics data (including location data comprising geocoordinate samples) and coordinating the same.

In one embodiment, the information regarding the various points for aserviceable address 600 can be uploaded to the mapping system 110,which, after sufficient telematics data (including location datacomprising geo coordinate samples) has been collected for a serviceableaddress 600, processes the information (e.g., sample geo coordinates)and stores information about the points in a record for thecorresponding serviceable address 600—see FIG. 9. For example, themapping system 110 may be configured to require two, three, or moreconsistent sample geo coordinates for a given point associated with aserviceable address before storing the information for the point in arecord for the serviceable address 600. Also, it should be noted thatthe mobile device 145 or data collection device 130 may receiveinformation about points for serviceable addresses as input from thedriver of the vehicle 100. Regardless, the mapping system 110 can storepoint information for each serviceable address in a record for theserviceable address, shown in FIG. 9.

In one embodiment, points for serviceable addresses may include, forexample, longitude and latitude coordinates, geocodes, altitude, course,speed, distance, UTC, and date information, or the like. Suchinformation may be stored in a record for the corresponding serviceableaddress as part of a digital map—as shown in FIG. 9. For instance, inthe examples shown in FIGS. 6-8, latitude and longitude information forthe four street network connection points 605 corresponding to theserviceable addresses 600 shown in these figures can be stored in one ormore records.

2. Geofence-Based Collection of Map Information

In one embodiment, geofences can be used to collect telematics data(including location data comprising geo coordinate samples) at eachserviceable address visited. In one embodiment, a computing entity(e.g., mapping system 110) may define one or more geofences aroundgeographic areas, such as serviceable addresses. The geofences may bedefined to surround a defined geographic area, such as surroundingcountries, regions, states, counties, cities, towns, interstates, roads,streets, avenues, toll roads, zip codes, area codes, ways, exit andentrance ramps, delivery routes, bus routes, taxis routes, industrialparks, neighborhoods, off-road areas (e.g., areas without paved roads),private land areas, parking areas, parcels, driveways, and/or the like.The geofences may be defined, for example, by the latitude and longitudecoordinates associated with various points along the perimeter of thegeographic area. Alternatively, geofences may be defined based onlatitude and longitude coordinates of the center, as well as the radius,of the geographic area. Geofences may be as large as an entire country,region, state, county, city, or town (or larger). The geographic areas,and therefore the geofences, may be any shape including, but not limitedto, a circle, square, rectangle, an irregular shape, and/or the like.Moreover, the geofenced areas need not be the same shape or size.Accordingly, any combination of shapes and sizes may be used inaccordance with embodiments of the present invention. Similarly, ageofence may overlap or reside wholly within another geofence. Forexample, a geofence of a parking area, for instance, may have geofencesdefined around stores or businesses in the parking area.

In one embodiment, after the one or more geofenced areas (e.g.,geofences) have been defined, the location of the vehicle 100 can bemonitored. Generally, the location of the vehicle 100 can be monitoredby any of a variety of computing entities, including the data collectiondevice 130, the mobile device 145, and/or the mapping system 110. Forexample, as noted above, the vehicle's 100 location at a particular timemay be determined with the aid of location-determining devices, locationsensors 120 (e.g., GNSS sensors), and/or other telemetry locationservices (e.g., cellular assisted GPS or real time location system orserver technology using received signal strength indicators from a Wi-Finetwork). By using the vehicle's 100 location, a computing entity (datacollection device 130, mobile device 145, or mapping system 110) candetermine, for example, when the vehicle 100 enters a defined geofence.

In one embodiment, in response to (parking area), a computing entity(e.g., the data collection device 130, mobile device 145, or mappingsystem 110) can collect, identify, and/or store/record relevanttelematics data. For example, the data collection device 130 cancollect, identify, and/or store/record telematics data (includinglatitude, longitude, direction, altitude, geocode, course, position,time, and/or speed data) about the area being traversed while within thegeofenced area. Similarly, the data collection device 130 can collect,identify, and/or store/record telematics data about where a delivery orpickup is made within the geofenced area. As will be recognized, avariety of other data (e.g., telematics data) can also be collected,identified, and/or stored/recorded, such as speed data, geofenced areadata (e.g., the triggering geofence), emissions data, engine data, tirepressure data, oil pressure data, idle data, meteorological data, imagedata, and/or the like. In one embodiment, the collected geocode and/ortelematics data can be routinely, periodically, and/or continuouslytransmitted to, for example, the mapping system 110.

In one embodiment, after the vehicle 100 has entered the geofenced area,the location of the vehicle 100 can continue to be monitored by any of avariety of computing entities. By using the vehicle's 100 location, acomputing entity can determine, for example, when the vehicle 100 exitsthe defined geofenced area. As described, this may include usinglocation-determining devices, location sensors 120 (e.g., GNSS sensors),or other telemetry location services (e.g., cellular assisted GPS orreal time location system or server technology using received signalstrength indicators from a Wi-Fi network).

In another embodiment, in response to (e.g., after) a determination thata vehicle 100 has exited the defined geofenced area (such as a streetnetwork), a computing entity can collect, identify, and/or store/recordrelevant data. For instance, the data collection device 130 can collect,identify, and/or store/record telematics data (including latitude,longitude, location, direction, altitude, geocode, course, position,time, and/or speed data) about the area being traversed outside thegeofenced area. Similarly, the data collection device 130 can collect,identify, and/or store/record telematics data about where a delivery orpickup is made outside the geofenced area. As described, a variety ofother data (e.g., telematics data) can also be collected, identified,and/or stored/recorded, such as speed data, emissions data, geofencedarea data (e.g., the triggering geofence), RPM data, tire pressure data,oil pressure data, idle data, meteorological data, and/or the like.Moreover, the collected geocode and/or telematics data can be routinely,periodically, and/or continuously transmitted to, for example, themapping system 110. Such collected data can then be stored in recordsand/or as data in a digital map, for example.

d. Defining Travel Paths in Parking Areas

Although digital maps typically include information about the location,shape, direction, and speed of street segments in a street network, suchinformation is not generally available for parking areas. For companiesthat have employees or vehicles 100 that traverse parking areas on aregular basis, understanding the travel paths in parking areas canassist such entities in the optimization of routing, scheduling,planning, and/or tracking processes.

1. Identifying Parking Areas

In one embodiment, identifying travel paths in parking areas may beginwith identifying a parking area in which there is at least one travelpath for the parking area that is not represented in a digital map(Block 500 of FIG. 5). FIGS. 7 and 8 show a parking area with at leastone travel path for the parking area not represented in the digital map.As can be seen from these figures, the parking area is surrounded byfour separate street segments of a street network. This particularparking area also has four street network connection points 605 foraccess to or from the street network for the two correspondingserviceable addresses 600.

In one embodiment, such parking areas may be identified using varioustechniques and approaches. In one embodiment, such parking areas can beidentified by the mapping system 110 from imagery of the parking areas(e.g., captured by one or more imaging devices 105). Imagery of aparking area may be captured by satellites, be captured as manned orunmanned aircraft fly over the parking area, and/or be captured byvehicles 100 traversing the parking area or by personnel traversing theparking area (collected manually or in response to various triggers).The parking areas may then be automatically determined from colorchanges, for example, in the imagery. In another embodiment, the mappingsystem 110 can also identify/determine parking areas from zoninginformation, surveys, building boundaries, identified business addresseswith delivery points that are not on the street network, and/or streetsegment data. In another embodiment, parking areas can determined basedon telematics data indicating when a vehicle 100 entered or exited astreet network from or to a parking area, such as being identified asoff-road travel (or off-street-network travel). The functionality foridentifying off-road travel (or off-street-network travel) is describedin U.S. Publ. Appl. 2012-0253861, which is incorporated herein in itsentirety by reference. Such determinations can be made by the mappingsystem 110 from the telematics data that was collected as previouslydescribed.

In another embodiment, the mapping system 110 can identify/determineparking areas from underlying layers in maps, such as base layers. Andin yet another embodiment, the mapping system 110 can identify/determineparking areas from user input. For example, a user may operate a mouseor other input device to manually draw a polygon around a parking areato identify the parking area as such to the mapping system 110. Usingyet another approach, when a driver of a vehicle 100 visits a parkingarea, the driver can enter input via the mobile device 145 indicatingthat he/she is traversing a parking area, then the telematics data(including location data comprising geo coordinate samples) can betagged, for example, as being associated with a specific parking area.In such a scenario, the driver of the vehicle 100 may also enter inputvia the mobile device 145 when he/she exits the parking area to indicatethat he/she is no longer traversing the parking area. As will berecognized, a variety of other approaches and techniques can be used toadapt to various needs and circumstances.

2. Identifying Street Network Connection Points for Parking Areas

After identifying a parking area in which there is at least one travelpath for the parking area that is not represented on a digital map, themapping system 110 can identify one or more street network connectionpoints 605 for the parking area (Block 505 of FIG. 5).

In one embodiment, identifying the street network connection points 605for a parking area may include first identifying the serviceableaddresses 600 for the parking area. For instance, the parking area shownin FIGS. 7-8 has two serviceable addresses that are accessible via orwithin the parking area. After identifying the serviceable addresses600, the mapping system 110 may identify the records corresponding tothose serviceable addresses and retrieve the corresponding streetnetwork connection points 605 for the same, which may be part of one ormore map layers of a digital map.

In an embodiment in which a user operates a mouse or other input deviceto manually draw a polygon around a parking area to identify the parkingarea as such to the mapping system 110, the mapping system 110 canidentify street network connection points 605 for the parking areaidentified within the polygon, for example. In another embodiment,street network connection points 605 can be identified based ontelematics data indicating when a vehicle 100 entered or exited a streetnetwork from or to a parking area, such as being identified as off-roadtravel (or off-street-network travel). The functionality for identifyingoff-road travel is described in U.S. Publ. Appl. 2012-0253861. Suchdeterminations can be made by the mapping system 110 from the telematicsdata that was collected as previously described.

3. Connecting Street Network Connection Points

After identifying the street network connection points 605 for a parkingarea, the mapping system can define one or more travel paths (e.g., afirst set of travel paths) in the parking area by connecting the one ormore street network connection points 605 in the parking area (Block 510of FIG. 5). In one embodiment, this may include the mapping system 110defining travel paths connecting the street network connection points605 using a matrix, lattice graph, mesh graph, grid graph, and/or thelike where each line defines a travel path within the parking areas.FIGS. 10 and 11 show an embodiment in which the mapping system 110 hasdefined travel paths in the parking area by connecting the four streetnetwork connection points 605.

The travel paths defined by the mapping system 110 in FIGS. 10 and 11run vertically, horizontally, diagonally, and/or the like. However, aswill be recognized, the travel paths can be defined in various ways toadapt to different needs and circumstances. For example, the travelpaths may be defined a configurable distance from one another. Forinstance, the travel paths may be defined every 25, 50, 75, or 100 feetvertically, horizontally, diagonally, and/or the like. This configurabledistance can be adjusted as desired. The travel paths can be defined toextend through one another or stop at intersecting points in the parkingarea. As will be recognized, the parking area travel paths can also bedefined in any concentration, shape, size, and/or design.

4. Known Obstructions

In one embodiment, after defining travel paths in the parking area, themapping system 110 can identify known obstructions in the parking area(Block 515 of FIG. 5). Such obstructions may be buildings, medians,flowerbeds, trees, ornamental structures, sidewalks, playgrounds,storage areas, signs, barricades, shopping cart returns areas, lightposts, and/or any other things that may prevent passage through orparking at the obstruction. In the parking area identified in FIGS. 6-8and 10-14, there are only two obstructions known to the mapping system110—the buildings for the serviceable addresses 600.

As with the street network connection points 605, the mapping system 110can identify known obstructions using a variety of techniques andapproaches. In one embodiment, identifying a known obstruction in aparking area may include identifying records corresponding to theserviceable address 600 and retrieving the corresponding pointinformation for the same, such as the freight delivery points, thepackage delivery points, the letter delivery points, the access points,the front door points, the back door points, the side door points,and/or the like, which may be part of one or more map layers of adigital map.

In another embodiment, a user can operate a mouse or other input deviceto manually draw a polygon around known obstructions to identify theknown obstructions as such to the mapping system 110. In anotherembodiment, known obstructions can be identified based on telematicsdata collected while traversing the parking area. And in yet anotherembodiment, the mapping system 110 can identify/determine suchobstructions from imagery of the parking area captured by satellites, bymanned or unmanned aircraft, and/or by vehicles 100 traversing theparking area or by personnel traversing the parking area (collectedmanually or in response to various triggers). In another embodiment, themapping system 110 can also identify/determine such obstructions fromsurveys, building boundaries, and/or the like. In certain embodiments,the physical dimensions of the known obstructions can also bedetermined, accessed, and/or obtained.

After identifying known obstructions, the mapping system 110 can removetravel paths defined in the parking area that overlap with the knownobstructions (Block 520 of FIG. 5). For example, for each knownobstruction, the mapping system 110 can remove known travel paths thatoverlap with the known obstruction. For instance, for the serviceableaddresses shown in FIGS. 6-8 and 10-14, the mapping system 110 canremove all travel paths that have been defined and overlap with thefreight delivery points, package delivery points, letter deliverypoints, access points, front door points, back door points, side doorpoints, dimensions of building structures or other obstructions, and/orthe like. That is, the mapping system 110 can remove all travel pathsthat have been defined and that overlap with such obstructions.

Additionally or alternatively, the mapping system 110 can remove alldefined travel paths that are within a configurable distance from knownobstructions. For example, for each known obstruction, the mappingsystem 110 can remove defined travel paths that are within aconfigurable distance of known obstructions. For instance, for theserviceable addresses shown in FIGS. 6-8 and 10-14, the mapping system110 can remove all travel paths that are within 25, 50, 75, and/or 100feet of the known obstructions. Such distances can be adapted to conformto a variety needs and circumstances. FIG. 12 shows an embodiment inwhich some of the travel paths defined in FIG. 11 are removed because ofknown obstructions.

As will also recognized, the known obstructions can be identified beforedefining the travel paths so that no travel paths are defined that wouldoverlap with or are not sufficiently offset from the known obstructions.In such an embodiment, the steps of Blocks 515 and 510 could beperformed in reverse and Block 520 could be eliminated. As will berecognized, though, a variety of other approaches and techniques can beused to adapt to various needs and circumstances.

In one embodiment, after defining the travel paths in the parking areaand removing any defined travel paths as described above, the mappingsystem 110 can update digital maps to represent the travel paths definedin the parking area. In another embodiment, the mapping system 110 canfurther process the travel paths by merging the defined travel pathswith collected telematics data.

5. Merging Defined Parking Paths with Collected Telematics Data

In addition to defining travel paths in parking areas, the mappingsystem 110 can use the telematics data (including location datacomprising geo coordinate samples) to plot/identify one or more actualtravel paths of vehicle 100 on a digital map. To do so, the mappingsystem 110 may load and display a base map. For example, in variousembodiments, the data comprising the base map may be stored on, andretrieved from, a variety of computing entities. Then, the mappingsystem 110 can review telematics data (including location datacomprising geo coordinate samples) that has been collected togenerate/provide a graphical representation of the one or more travelpaths of vehicles 100 in a parking area. In one embodiment, the mappingsystem 110 can accomplish this by plotting/identifying each individuallocation data point from the collected telematics data on the mapdisplay and then connecting the plotted/identified location points inchronological order with lines displayed over the base map. In variousembodiments the travel paths generated by the mapping system 110 maycomprise a line with various distinguishing characteristics, such ascolor and thickness variations. FIG. 13 shows the travel pathsplotted/identified by the mapping system 110 as determined from thetelematics data collected by one or more vehicles 100 over a period oftime.

In one embodiment, the travel paths that are plotted/identified based onthe collected telematics data (including location data comprising geocoordinate samples) can be merged/combined with the travel paths definedby connecting the one or more street network connection points 605 inthe parking area. For instance, the travel paths shown as being definedin FIG. 12 (first set of travel paths) can be merged/combined with thetravel paths shown in FIG. 13 (second set of travel paths). In oneembodiment, in combining/merging the two sets of travel paths, themapping system 110 may retain all the travel paths represented from bothsets. In another embodiment, the mapping system 110 can give precedenceto one of the sets of travel paths, such as the travel pathsidentified/determined from the collected telematics data since a vehicle100 actually traversed those points. FIG. 14 represents the parking areaafter merging/combing the two sets of travel paths. As can be seen fromthis figure, the mapping system 110 removed some of the travel pathsdefined by connecting the street network connection points 605. As willbe recognized, a variety of other approaches and techniques can also beused to adapt to various need and circumstances.

In one embodiment, the mapping system 110 can update maps to representthe travel paths of parking areas that have been defined,identified/determined, and/or merged/combined. For example, the mappingsystem 110 can update the parking areas in maps to include the varioustravel paths that have been defined or identified/determined. This mayinclude updating the one or more map layers to accurately reflect thetravel paths in parking areas.

e. Optimizing Routes and/or Providing Directions

In one embodiment, with the travel areas of parking areas being storedas part of a digital map, the mapping system 110 can better determine orprovide information about traveling to or accessing serviceableaddresses 600 within or accessible by parking areas. In that regard,delivery route and/or directions, for example, using a set ofserviceable addresses 600 can be optimized to take into account travelwithin parking areas, traversing parking areas from one serviceableaddress to another, and/or the like. This may include creating time anddistance matrices and or a variety of other approaches and techniques toadapt to various needs and circumstances.

In one embodiment, such routing may include providing directions and/orrouting information (including travel paths in parking areas) forrouting to front doors, back doors, side doors, and/or any other pointstored in the corresponding records. Such routing may be based onvehicle type. For example, all passenger vehicles 100 may be routed tothe front door of serviceable addresses 600, while commercial vehicles100 may be routed to back or side doors of serviceable addresses 600.The vehicle type may be input received from a user or be automaticallydetected or provided based on telematics data. As will be recognized, avariety of other approaches and techniques can be used to adapt tovarious needs and circumstances.

IV. CONCLUSION

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

1. A method for defining travel paths in parking areas, the methodcomprising: for a parking area in which there is at least one travelpath for the parking area that is not represented on a digital map,defining, by one or more processors, a first set of one or more travelpaths in the parking area by identifying one or more paths traversed byone or more vehicles in the parking area based at least in part ontelematics data collected while the one or more vehicles were traversingthe parking area; and updating, via the one or more processors, thedigital map to include a representation of the first set of one or moretravel paths in the parking area.
 2. The method of claim 1 furthercomprising: identifying one or more street network connection points forthe parking area, the one or more street network connection pointsproviding the ability to enter the parking area from a street network,exit the parking area to the street network, or both; and defining asecond set of one or more travel paths in the parking area by connectingthe one or more street network connection points in the parking area. 3.The method of claim 2 further comprising merging the first set of one ormore travel paths with the second set of one or more travel paths. 4.The method of claim 1 further comprising: identifying a knownobstruction in the parking area; and removing travel paths defined inthe parking area that overlap with the known obstruction.
 5. The methodof claim 4, wherein removing the travel paths defined in the parkingarea that overlap with the known obstruction further comprises removingtravel paths defined in the parking area that are within a configurabledistance of the known obstruction.
 6. The method of claim 1, whereindefining the second set of travel paths in the parking area byconnecting the one or more street network connection points in theparking area further comprises defining travel paths in the parking areausing one selected from the group consisting of a grid, a lattice, and amatrix.
 7. An apparatus comprising at least one processor and at leastone memory including computer program code, the at least one memory andthe computer program code configured to, with the processor, cause theapparatus to at least: for a parking area in which there is at least onetravel path for the parking area that is not represented on a digitalmap, define a first set of one or more travel paths in the parking areaby identifying one or more paths traversed by one or more vehicles inthe parking area based at least in part on telematics data collectedwhile the one or more vehicles were traversing the parking area; andupdate the digital map to include a representation of the first set ofone or more travel paths in the parking area.
 8. The apparatus of claim7, wherein the memory and computer program code are further configuredto, with the processor, cause the apparatus to: identify one or morestreet network connection points for the parking area, the one or morestreet network connection points providing the ability to enter theparking area from a street network, exit the parking area to the streetnetwork, or both; and define a second set of one or more travel paths inthe parking area by connecting the one or more street network connectionpoints in the parking area.
 9. The apparatus of claim 8, wherein thememory and computer program code are further configured to, with theprocessor, cause the apparatus to merge the first set of one or moretravel paths with the second set of one or more travel paths.
 10. Theapparatus of claim 7, wherein the memory and computer program code arefurther configured to, with the processor, cause the apparatus to:identify a known obstruction in the parking area; and remove travelpaths defined in the parking area that overlap with the knownobstruction.
 11. The apparatus of claim 10, wherein removing the travelpaths defined in the parking area that overlap with the knownobstruction further comprises removing travel paths defined in theparking area that are within a configurable distance of the knownobstruction.
 12. The apparatus of claim 7, wherein defining the secondset of travel paths in the parking area by connecting the one or morestreet network connection points in the parking area further comprisesdefining travel paths in the parking area using one selected from thegroup consisting of a grid, a lattice, and a matrix.
 13. A computerprogram product comprising at least one non-transitory computer-readablestorage medium having computer-readable program code portions storedtherein, the computer-readable program code portions comprising: anexecutable portion configured to, for a parking area in which there isat least one travel path for the parking area that is not represented ona digital map, define a first set of one or more travel paths in theparking area by identifying one or more paths traversed by one or morevehicles in the parking area based at least in part on telematics datacollected while the one or more vehicles were traversing the parkingarea; and an executable portion configured to, update the digital map toinclude a representation of the first set of one or more travel paths inthe parking area.
 14. The computer program product of claim 13 furthercomprising: an executable portion configured to identify one or morestreet network connection points for the parking area, the one or morestreet network connection points providing the ability to enter theparking area from a street network, exit the parking area to the streetnetwork, or both; and an executable portion configured to define asecond set of one or more travel paths in the parking area by connectingthe one or more street network connection points in the parking area.15. The computer program product of claim 14 further comprising anexecutable portion configured to merge the first set of one or moretravel paths with the second set of one or more travel paths.
 16. Thecomputer program product of claim 13 further comprising: an executableportion configured to identify a known obstruction in the parking area;and an executable portion configured to remove travel paths defined inthe parking area that overlap with the known obstruction.
 17. Thecomputer program product of claim 16, wherein removing the travel pathsdefined in the parking area that overlap with the known obstructionfurther comprises removing travel paths defined in the parking area thatare within a configurable distance of the known obstruction.
 18. Thecomputer program product of claim 13, wherein defining the second set oftravel paths in the parking area by connecting the one or more streetnetwork connection points in the parking area further comprises definingtravel paths in the parking area using one selected from the groupconsisting of a grid, a lattice, and a matrix.